Is it backwards-compatible with Airflow 2?

@potiuk logical_date property was added back in 2021

logical_date teproperty was added back in 2021

I know, just checking if it is ok to change it in the provider - which will be (for the next 6 months or so) only installed on Airflow 2 :)

Simply execution_date and logical_date have different semantics, so my question is, if that will impact observed open-lineage events. And if so - whether it should be somehow explained in the changelog so that users are not surprised.

@potiuk does it really have different semantics?

From what I can find, it's essentially a rename:

From AIP-39

We need a single date value that is the "canonical" date for the DagRun date, that can be used for sorting DagRuns for the UI view, so the current "execution_date" column on DagRun needs to be kept, but we should rename - and we've chosen "logical_date".

Also in the docstring:

This replaces execution_date in Airflow 2.1 and prior. The idea is essentially the same, just a different name.

Basically, we want the same: the time when the DagRun is scheduled to be run, without consideration if it's actually going to run at that time, due to scheduler being backed up or other reason.

Basically, we want the same: the time when the DagRun is scheduled to be run, without consideration if it's actually going to run at that time, due to scheduler being backed up or other reason.

Yep. You are right. I had confused it with "start/end interval" and other macros available in context, but logical_date and execution_date are really aliases.